Original problem, how to reproduce:

#include <etl/delegate.h>

namespace ctx {
struct os {};
struct any {
  any() = default;
  any(os) {}
};
} // namespace ctx

struct Test {
    etl::delegate<void(ctx::os)> GetCb() {
      return etl::delegate<void(ctx::any)>::create<Test,
      &Test::CbAnyCtx>(
          *this);
    }

private:
  void CbAnyCtx(ctx::any ctx) {}
};

int main() {
  Test().GetCb()(ctx::os{});
  etl::delegate<void(void)> f = []() {};
  return 0;
}

This compiles and does not look suspicious at the first glance but results in a segmentation fault at runtime.

What happens here:

1. A delegate is created etl::delegate<void(ctx::any ctx)>::create<Test, &Test::CbAnyCtx>(*this);
2. But we need a etl::delegate<void(ctx::os ctx)>, the compiler selects the constructor from const TLambda&.
3. Note that etl::is_same<etl::delegate<TReturn(TParams...)>, TLambda>::value is false because the signatures of the delegates do not match
4. The newly created delegate is returned and the first delegate is destroyed. Now the second delegate holds a dangling pointer

This PR attempts to fix this issue by using a reliable method for checking if a functor is a delegate